disableInitialSync feature flag #2835
Conversation
✅ Deploy Preview for devspace-docs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Thanks for the PR!
Instead of adding a new flag, what would you think of adding another InitialSyncStrategy, named none or disabled?
This should reduce the number of changes. The docs would need to be updated here to document the new strategy.
Additionally, an e2e test would help to avoid regressions in the future. I can assist if needed, since the initial sync strategies aren't well tested at the moment.
rcelestino
force-pushed
the
rcelestino/improve_featureflag_disableinitialsync
branch
3 times, most recently
from
9e0d227 to
e8ae032
Compare
Adding support to disable the initial sync using the same initialSync strategy configuration. Signed-off-by: Roberto Celestino <rcelestino@gmail.com>
rcelestino
force-pushed
the
rcelestino/improve_featureflag_disableinitialsync
branch
from
e8ae032 to
2953f49
Compare
|
@lizardruss changed and added e2e.
|
What issue type does this pull request address? (keep at least one, remove the others)
/kind enhancement
/kind feature
What does this pull request do? Which issues does it resolve? (use
resolves #<issue_number>if possible)Partially resolves #1218 adding support to disable completely the initial sync
Please provide a short message that should be published in the DevSpace release notes
Enhance the configuration capabilities of DevSpace to enable the possibility of disabling the initial sync, similar to how you can currently disable the upload or download.
What else do we need to know?
There are use cases where syncing is required only for files changed after the development or sync process has been initiated, rather than fully synchronizing the remote or local repository.